Description

Creates a partners overrides file similar to the public site so that we can customize some strings.

How Can This Be Tested/Reviewed?

This is relevant for this LA PR that is trying to override the strings for two "How did you hear?" options. We need to ensure the override happens on both public and partners. We also have other partners strings we need to override, and in new Detroit we just did it directly in the partners general file which we want to avoid.

Author Checklist:

• Added QA notes to the issue with applicable URLs
• Reviewed in a desktop view
• Reviewed in a mobile view
• Reviewed considering accessibility
• Added tests covering the changes
• Made corresponding changes to the documentation
• Ran yarn generate:client and/or created a migration when required

Review Process:

• Read and understand the issue
• Ensure the author has added QA notes
• Review the code itself from a style point of view
• Pull the changes down locally and test that the acceptance criteria is met
• Either (1) explicitly ask a clarifying question, (2) request changes, or (3) approve the PR, even if there are very small remaining changes, if you don't need to re-review after the updates